S3Drive - MacOS S3Drive Hangs a couple minutes after starting

My S3Drive app has started crashing a few minutes after starting up. I can restart it, but then again it will crash after a few minutes. Has been running great for a while until this started a few days ago.

Hi, Thanks for your message. I am wondering if timing lines up with e.g. sync job starting. Have you configured any within S3Drive? By any chance can you confirm if app freeze matches with any particular Sync entry that might be running in that moment? The other bit that could potentially cause this is drive mount starting up warming it's listing cache, but any freeze/slow down would like happen in the first few seconds, instead of few later minutes. Do you use mount by the way? (edited)

Interesting, yes, it does seem to line up with one of my sync jobs starting up. I do use the mount function as well. I'll try and stop the sync job and see if that fixes the issue

8:43 PM

Maybe not. I paused that sync job but it still crashes. Turned off the drive mount as well but no change. Crashes within about 30 seconds of start up.

Looks like stopping all 3 of my sync jobs has done the trick of keeping the application running. I'll go one by one and see which is causing the problem.

Found the one sync job that's causing the issue. There is a 90GB Macos Photos database file in there and not much else. Everytime I try to restart the sync on that job the app fails, so something is going on there.

We're also fighting this issue for quite a while. This seems to be related to macOS and Rclone only. The way that macOS handles processes / threads works differently that on other OS's and despite our efforts to isolate Rclone jobs, so they use spare "work threads" instead of main rendering thread. It still sometimes happen as if macOS decide that the main thread isn't busy, so "let's not waste the CPU resources and assign heavy task to it" - that makes the app UI unusable. Fix is likely couple lines / config changes long, only if we knew what to tweak. May I have your machine spec and OS version please? Reasonable start from our end, would likely be to provide configurable number of concurrent threads/transfers, so user could tweak that number and see if it helps on their end. We're really keen to have this resolved! (edited)

You bet. I'm running an M2 Mac Mini, 8GB RAM, MacOS 15.1. Thanks!

Hi, by any chance, can you update to 1.10.5 on macOS and see if there is any change on this? We've updated some dependencies (including Rclone) and improved thread configuration.